 x	E                                                                 ssages dealing with CPM/EOS transfers. 
 
TO TOM KEENE FROM: DAN WESTBROOK 
SUBJ: EOS <---->CPM 
 I recently asked how to UPLOAD an EOS file to this BBS,FROM THE SOCA BBS , 24 hrs. 7l4-773-l603, & IEAUG comes the following exchange of messages dealing with CPM/EOS transfers. 
 
TO TOM KEENE FROM: DAN WESTBROOK 
SUBJ: EOS <---->CPM 
 I recently asked how to UPLOAD an EOS file to this BBS, rather than use the IMAGE2.COM whole disk method for transferring an EOS Disk (145K of it at 
least) or CP/M Disk to a 
CP/M Data Disk to use with 
IMP or MEX. What is the 
EASIEST METHOD, Tom? I 
would strictly be using a 
standard 160K set of Disk 
Drives. 
 
 
TO: Dan Westbrook FROM: KEENE, Thomas J. 
SUBJ: Reply to A709 
Easy is as easy does. I guess it's whatever you're most familiar with. I see little point in IMAGING a whole disc and then transferring the image file with a CP/M modem program if you are just 
wanting to send one file. 
Those articles I uploaded 
to Zonker pretty well 
cover the conversion of an 
EOS file to CP/M and vice 
versa. Going from EOS to 
CP/M will REQUIRE that you 
filter the file after it 
has been converted to a 
CP/M file. Otherwise line 
feeds and other important 
stuff will be missing. 
Also, if you do filter the 
file, all control 
characters will be 
stripped off in the 
process. This means that 
nice things like 
underlining will be 
eliminated. That, too, can 
be remedied, but this 
isn't the place to go into 
that. I have also written 
an extensive article on 
underlining test in CP/M. 
Actually it is extremely 
easy to ADAM a file from 
EOS to CP/M and then 
filter it. It only takes a 
few minutes. BUT, remember 
that an EOS SMARTWRITER 
file does not necessarily 
have a carriage return at 
the end of each line, the 
way CP/M does. ADAM 
internally will wrap 
around until you get tired 
of it. Often, many 
EOS/SMARTWRITER files may 
have a carriage return 
only at the end of a 
paragraph. This would be 
devastating when put into 
CP/M format. Your printer 
would type a line and when 
it got to the right edge, 
it would just sit there 
waiting for a carriage 
return. And without line 
feeds, even if it got a 
carri waiting for a 
carriage return.  
If it wasn't filtered, 
there would be no line 
feeds even if there were 
carriage returns. This 
means that the printer 
would type a line on top 
of previous lines. A 
mess!. But if you read 
thos articles or refer to 
back issues of the 
newsletter, you can make 
perfect CP/M copies of EOS 
files. And it isn't very 
hard. At least I don't 
think so. As far as I am 
aware of, there is no way 
to bundle EOS files 
together. In CP/M there 
are a couple of ways to do 
that. One is a library 
file and another is an 
archive file. AND of 
course, the IMAGE file. In 
EOS, you have to transmit 
the DOC files separately 
from the program files. 
And there is no 
compression techniques for 
EOS. I think that 
conversion to CP/M is the 
way to fly. That's not to 
say that I haven't 
uploaded and downloaded a 
lot of EOS files with 
ADAMLINK. It works real 
fine on other BBS. I have 
never tried it on this 
BBS. It seems to me that 
it should work OK. Any 
way, have a go at it. You 
have nothing to lose.  
 See you soon......... Tom 

 
there would be no line 
feeds even
